Elvis Preslie
NRDS Securities
Apocalypse Now.
23
   |
Posted - 2013.03.25 05:14:00 -
[1] - Quote
Flying cheetah with inertia stab, mwd, covert cloak (covert ops lvl 4)
04:21:38GenericJumping from Auga to Kourmonen
04:20:57NotifyCovert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next Less than one second.
04:20:57NotifyCovert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next Less than one second.
04:20:56NotifyCovert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next 1 second.
04:20:55NotifyCovert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next 2 seconds.
04:20:54HintLimited 1MN Microwarpdrive I is already active
04:20:54NotifyCovert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next 3 seconds.
04:20:53NotifyInterference from the cloaking you are doing is preventing your systems from functioning at this time.
04:20:52NotifyAligning to Kourmonen
04:20:40GenericJumping from Amamake to Auga
After jump from amamake to auga, the covert cloak was NOT activated again, it was attempting to be activated but always failed while the mwd worked unusually fine.
Sometime I think certain parts of systems are intentionally bugged to make people lose something, those that havent lost anything in forever, like how it uncloaks itself without a ship or object being around (hasnt happened to me in a long time though, way before retribution or inferno); everyone knows of the uncloak bug.
Then, when people lose things because of these bugs, we get responses like "unable to reproduce or unable to verify" and blamed is the machine the client is running on.
This machine does not crash or even disconnect (socket closed) like most others are having; the point where others see the "socket closed" message, my machine recovers from the glitch in the eve engine and continues on; i use longer than normal UDP/TCP timeouts along with checksums.
speaking of another recent bug, I have a huge feeling that the socket closed bug is coming from the patching, instead of fixing, the memory hole errors that i DID have long ago. I reported the memory hole in another bug report; its very few certain things that, when rendered, would cause eve to start eating memory slowly, until it got up to 16 GB of memory used (the max of the machine). it would then crash.
When this starts happening, you guys made eve refresh its memory commit its using INSTEAD of fixing the root cause that makes the hole. This is why my eve freezes after the memory hole has been triggered and other people's pc's timeout quicker when mine waits for new ACK from TCP.
The simple fact is the second I align, seeing as it takes more than three seconds to jump, I should be able to activate cloak with one Function key press instead of having to tap it two or more times. Your lead programmer resigned, whom caused the majority of bugs you guys did a good of fixing in retribution. WHY cant we get the rest of his screwups out of eve, like this problem of clients being non responsive between session changes.
During a session change, I should be able to keep typing to others without the window focus being changed to another window or inhibit me from doing tasks; you try typing this bug report while traveling.
I know bugs still exist in eve that I've reported a year ago, yet to be fixed, including the HUGE mining exploit.
STop adding stuff to eve before making sure you have a version of eve without ONE hitch in it. You've added dust and the patch in june is fine, while I hope it fixes some or all of what I said; however, after the june patch, you need to address every bug report in the system before moving on, especially the two issues i mentioned above.
Stop patching code; rework it to be more fluent for the cpu's. It only causes more unforseen bugs when you patch, the reason the programmer probably resigned, as he realized the mess he piled up on himself and caused you guys.
I KNOW this is how parts of eve are being written, as its evident not only playing eve but in the diagram for the old criminality system alone.
>MOST IMPORTANTLY< release a 64-bit version of exefile.exe which will help a lot in programming, preventing bugs, and increase client responsiveness. We're being limited to 3GB on 32-bit process when we have 16GB or so available.
|